Configuring the Azure Logic Apps Logging and Monitoring Agent
Info
This guide teaches the basics about how to configure the Nodinite Azure Logic Apps Logging and Monitoring Agent to enable Monitoring and Logging of Logic Apps in your Azure Subscriptions. Please read the 'About Logic Apps Logging options' user guide before you continue.
- Subscription Configuration - Learn about how to configure a Subscription with Logic App Workflows to include in the Monitoring and Logging.
Note
The Monitoring and the remote configuration is available if you first install and create the initial Monitoring Agent Configuration for the Azure Logic Apps Logging and Monitoring Agent. First-time users start here.
Remote Configuration
As a Nodinite Administrator, click on the 'Configuration' button to open a modal to configure the Agent:
Click the 'Configuration' button to open a dialog for configuring the agent.
You can perform specific configurations directly on Resources using the Action button, given that the Role of the Monitor View has the Remote Actions feature enabled.
Info
You must be a Nodinite Administrator to manage Azure Subscriptions with Azure Logic Apps.
Settings tab
From within the Settings tab, you provide some details that determine the operation behaviour of the Azure Logic Apps Logging and Monitoring Agent.
- Environment
- Debug
- Culture Information
- Agent database connection string
- Days to keep running and failed workflow runs
- Days to keep running and failed workflow runs
Environment
As part of the common features shared with all Monitoring Agents is an option to set the name of the target Environment, for example, TEST, QA, PROD.
Debug
Part of the common features shared with all Monitoring Agents, is an option to set the Debug flag for additional file logging that can be enabled/disabled as needed. Default is unchecked.
Culture Information
The Culture Information setting determines how time-based data from this Agent presents in the Web Client/Web API.
Agent database connection string
The Nodinite Azure Logic Apps Logging and Monitoring Agent is using a SQL Server Database to store data. Among other things, this database holds data about the number of retries resubmitting failed runs. This feature is unique with Nodinite.
Server=localhost;Database=Nodinite_Agent_AzureLogicApps;Integrated Security=SSPI;Connection Timeout=60;TrustServerCertificate=True
Here's an example of a Connection String.
Days to keep running and failed workflow runs
- Days to keep running and failed workflow runs - Specify the number of days to keep the running and failed runs until marked for deletion in the Agent database (Default = 180 days)
Days to keep successful workflow runs
- Days to keep successful workflow runs - Specify the number of days to keep the running and failed runs until marked for deletion in the Agent database (Default = 7 days)
Save
You must click 'Save' or 'Save and close' for changes to persist. The new settings/thresholds are evaluated on the next synchronization.
Here's an example of the Save options.
Note
The delay in presenting the new evaluated state depends on the synchronization interval set for the Monitoring Agent. Click the Sync Now button to force an immediate synchronization.
Save and close, save, and close the dialogue.
Cancel, closes the dialogue without saving any changes.
Add Azure Logic Apps Logging and Monitoring Agent Configuration
After successfully installing the Nodinite Azure Logic Apps Logging and Monitoring Agent, you must provide connection details so the Monitoring Service knows there's a new guy in town.
There is no Monitoring or Logging in the Azure Logic Apps Logging and Monitoring Agent before the steps outlined below has been performed.
Configuration Steps
- Add and configure a new Monitoring Agent Configuration
Connection information is available in the
README.txt
file in the installation folder
- Use the Remote Configuration feature to configure the Agent. Detailed at the beginning of this user guide.
- Create one or more self-service enabled Monitor Views that include the selected Resources provided by the Azure Logic Apps Logging and Monitoring Agent according to business needs.
- Fine-tune specific settings directly on Resources using Remote Actions
How do I grant my users access to logic apps monitoring?
This is detailed in the User access to Logic Apps Monitoring guide.
How do I grant my users access to logic apps logging?
This is detailed in the User access to Logic Apps Logging guide.
Next Step
- Subscription Configuration
- Add or manage a Monitoring Agent Configuration
- Add or manage Monitor View
- User access to Logic Apps Monitoring